Questions
10 of 24
1What are the SOLID principles? Explain each briefly.
2Explain the Single Responsibility Principle (SRP) with an example.
3Explain the Open/Closed Principle (OCP). How do you achieve it without modifying existing code?
4Explain the Liskov Substitution Principle (LSP). What happens if it's violated? (Square/Rectangle problem)
5Explain the Interface Segregation Principle (ISP). Why are fat interfaces bad?
6Explain the Dependency Inversion Principle (DIP). How does it relate to Dependency Injection?
7What is the difference between Aggregation and Composition?
8What is the Factory Pattern? How does it help in achieving OCP?
9What is the Abstract Factory Pattern? How does it differ from Factory Method?
10What is the Strategy Pattern? How does it replace complex conditional logic?
11What is the Observer Pattern? Where is it used in real life? (Event handling, Pub/Sub)
12What is the Decorator Pattern? How does it add functionality dynamically?
13What is a Singleton Pattern? What are the thread-safety concerns and how to handle them?
14What is an Anti-Pattern? Can you name a few? (God Object, Spaghetti Code, Golden Hammer)
15What is "Coupling" and "Cohesion"? Explain the relationship between them.
16What are Generics/Templates? How do they improve type safety and performance compared to casting?
17What is Type Erasure (Java) vs Reified Generics (C#)?
18What is Variance in Generics? (Covariance and Contravariance)
19What are Extension Methods (C#) or Default Methods (Java)? When should you use them?
20What is Reflection? How can it be used to break Encapsulation? What are the performance costs?
21What is the "Law of Demeter"? (Don't talk to strangers)
22Explain "Tell, Don't Ask" principle.
23What is the DRY principle? How does OOP help achieve it?
24What is the YAGNI principle?
10 / 24

What is the Strategy Pattern? How does it replace complex conditional logic?

Difficulty: 3/10

Strategy Pattern

The Strategy Pattern encapsulates interchangeable algorithms behind a common interface and allows the algorithm to be selected independently of the client. It is particularly effective when a method contains a growing if/else or switch statement representing different business rules. Instead of repeatedly modifying the client, I introduce a strategy per behavior and inject or select the required strategy.

javascript
  1. 1

    Encapsulates algorithms behind a common abstraction.

  2. 2

    Removes growing conditional logic from the context class.

  3. 3

    Strategies can be tested independently.

  4. 4

    New strategies can often be added without changing existing client logic.

  5. 5

    Use it when behavior genuinely varies; avoid it for trivial one-off conditions.

Follow-up Questions

  • How does Strategy support OCP?
  • Strategy vs State pattern?
  • How can strategies be selected dynamically?
  • When is a switch statement better than Strategy?
Share

Share via WhatsApp, X, Facebook, LinkedIn or copy link. Open Graph preview enabled.